Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff66d5c0ed60de6c8b3f6425c880e51367f01a483c55918e584634e82ba49521

Tx prefix hash: 815c9ddd5a7abe1c67397fe14184e5d9613463fdbfcb07dfc8378a868c707460
Tx public key: 669b295bf76460701a21e5f6449d280989b2d43a6c09d2a3aefd59d9b4e7e599
Timestamp: 1674250868 Timestamp [UCT]: 2023-01-20 21:41:08 Age [y:d:h:m:s]: 01:291:10:56:58
Block: 679146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469264 RingCT/type: yes/0
Extra: 01669b295bf76460701a21e5f6449d280989b2d43a6c09d2a3aefd59d9b4e7e59902110000000274b6d784000000000000000000

1 output(s) for total of 3.449112174000 dcy

stealth address amount amount idx
00: 2caec6c02aad3114ea5dacbd0e6cd058d2dbc6d89d4041e30fded38852da1d39 3.449112174000 1121111 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": 679156, "vin": [ { "gen": { "height": 679146 } } ], "vout": [ { "amount": 3449112174, "target": { "key": "2caec6c02aad3114ea5dacbd0e6cd058d2dbc6d89d4041e30fded38852da1d39" } } ], "extra": [ 1, 102, 155, 41, 91, 247, 100, 96, 112, 26, 33, 229, 246, 68, 157, 40, 9, 137, 178, 212, 58, 108, 9, 210, 163, 174, 253, 89, 217, 180, 231, 229, 153, 2, 17, 0, 0, 0, 2, 116, 182, 215, 132, 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