Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9554a82af5330c4cfcc7ad62b5649fab617e95b5f83c042445ba976ffe37f5cb

Tx prefix hash: c0e93a5aba1c35d639adc125737bac7681960eeac89857b7f67b06f99dff215e
Tx public key: 86d6504aa77cf85673af54588a616195c3c7b2e48f47b497b3f5aa38e193e7cb
Timestamp: 1736028220 Timestamp [UCT]: 2025-01-04 22:03:40 Age [y:d:h:m:s]: 00:162:16:17:48
Block: 1190307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115983 RingCT/type: yes/0
Extra: 0186d6504aa77cf85673af54588a616195c3c7b2e48f47b497b3f5aa38e193e7cb021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f90dc3ec4525b990aa6f6aa74a07fbcbd0e852320473738781e647f37a6a2bc4 0.600000000000 1676822 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": 1190317, "vin": [ { "gen": { "height": 1190307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f90dc3ec4525b990aa6f6aa74a07fbcbd0e852320473738781e647f37a6a2bc4" } } ], "extra": [ 1, 134, 214, 80, 74, 167, 124, 248, 86, 115, 175, 84, 88, 138, 97, 97, 149, 195, 199, 178, 228, 143, 71, 180, 151, 179, 245, 170, 56, 225, 147, 231, 203, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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