Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f0a75978805aee62ebfb580d2c6ce90ea6a5df375507aadc205b27ba509b965

Tx prefix hash: 2a61439fed320524548b31cdd4d7b1d5091c7ffd2401122e800374b5bceffa1b
Tx public key: f02ef51e6243997223fd3a9bd891a3423c7c6d7eb1fca9242a06d78ee5e542c2
Timestamp: 1706613062 Timestamp [UCT]: 2024-01-30 11:11:02 Age [y:d:h:m:s]: 01:076:03:04:10
Block: 946550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315488 RingCT/type: yes/0
Extra: 01f02ef51e6243997223fd3a9bd891a3423c7c6d7eb1fca9242a06d78ee5e542c202110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5c519dcbd3e2b96e670f152f65f87348e3641f204c16e74a0f312f8125a7639 0.600000000000 1404882 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": 946560, "vin": [ { "gen": { "height": 946550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5c519dcbd3e2b96e670f152f65f87348e3641f204c16e74a0f312f8125a7639" } } ], "extra": [ 1, 240, 46, 245, 30, 98, 67, 153, 114, 35, 253, 58, 155, 216, 145, 163, 66, 60, 124, 109, 126, 177, 252, 169, 36, 42, 6, 215, 142, 229, 229, 66, 194, 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