Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 7678a0bd10f17c3d0b0ea45073415ba05b382365d830bb434e490a76e3ee242d

Tx prefix hash: 80783de6cc7818aa69efbf13fbec1f710dcd13022b3dfc2a2f7396a6b472780e
Tx public key: 434429175f67ce5c5fd593f37c8c2aa7b47dd4edf0d00964acd1ac5d2fd78287
Timestamp: 1705160572 Timestamp [UCT]: 2024-01-13 15:42:52 Age [y:d:h:m:s]: 01:083:21:44:42
Block: 934516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321054 RingCT/type: yes/0
Extra: 01434429175f67ce5c5fd593f37c8c2aa7b47dd4edf0d00964acd1ac5d2fd7828702110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f15d89c8756e38464ad06d94b0d12013d8b78467be3eb00eceb881206b36700 0.600000000000 1392530 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 934526, "vin": [ { "gen": { "height": 934516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f15d89c8756e38464ad06d94b0d12013d8b78467be3eb00eceb881206b36700" } } ], "extra": [ 1, 67, 68, 41, 23, 95, 103, 206, 92, 95, 213, 147, 243, 124, 140, 42, 167, 180, 125, 212, 237, 240, 208, 9, 100, 172, 209, 172, 93, 47, 215, 130, 135, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8