Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9a9304ff7e3bb00a5c736e494c4890487ef4e56b44588cffcdb432e0b72be1d

Tx prefix hash: b4a11b352d7df8424aa39d560c0ca597eb677f69bdad664717c0bcdc3d87dc5f
Tx public key: 764cb8f55bb393069074d935d96cdfedbfafd2e581cc0dc3d023ab1963b5027f
Timestamp: 1696574274 Timestamp [UCT]: 2023-10-06 06:37:54 Age [y:d:h:m:s]: 02:031:10:06:42
Block: 863543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542071 RingCT/type: yes/0
Extra: 01764cb8f55bb393069074d935d96cdfedbfafd2e581cc0dc3d023ab1963b5027f021100000008faf35c9c000000000000000000

1 output(s) for total of 0.844741060000 dcy

stealth address amount amount idx
00: e0fceb1e6c16842b1b7552983016246206f649fa2b420376d2b1c96f84660955 0.844741060000 1318001 of 0

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": 863553, "vin": [ { "gen": { "height": 863543 } } ], "vout": [ { "amount": 844741060, "target": { "key": "e0fceb1e6c16842b1b7552983016246206f649fa2b420376d2b1c96f84660955" } } ], "extra": [ 1, 118, 76, 184, 245, 91, 179, 147, 6, 144, 116, 217, 53, 217, 108, 223, 237, 191, 175, 210, 229, 129, 204, 13, 195, 208, 35, 171, 25, 99, 181, 2, 127, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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