Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b10b582f7702884bfd44f61d91dcc0b6ec690070e51835e0c93dfd23a5eb5d78

Tx prefix hash: 8e1d9eda48903f6060b18b691f27ac2dace001ac81a859daf57cfdd8eebcf7ab
Tx public key: f7d8ba5e36e3a3997d9a284f98ee19bcd4c1375e411d61ea1bc28726021b3cdf
Timestamp: 1710581764 Timestamp [UCT]: 2024-03-16 09:36:04 Age [y:d:h:m:s]: 01:005:14:59:42
Block: 979496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264976 RingCT/type: yes/0
Extra: 01f7d8ba5e36e3a3997d9a284f98ee19bcd4c1375e411d61ea1bc28726021b3cdf02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16ad200623dec6744f04c2fc58673e4495989f400fd35f3914c59082258d0305 0.600000000000 1439529 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": 979506, "vin": [ { "gen": { "height": 979496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16ad200623dec6744f04c2fc58673e4495989f400fd35f3914c59082258d0305" } } ], "extra": [ 1, 247, 216, 186, 94, 54, 227, 163, 153, 125, 154, 40, 79, 152, 238, 25, 188, 212, 193, 55, 94, 65, 29, 97, 234, 27, 194, 135, 38, 2, 27, 60, 223, 2, 17, 0, 0, 0, 5, 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