Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73f57f3b3056b35b892270da3d3ade262569f2390ec2e6dfe3db10b87dd6eb5a

Tx prefix hash: 0d6c8c36e9c137bb17769bc6ef624b3df90f9db6b8fca2a2160fe6ca9c30a828
Tx public key: e51605cdff15ebe082d5cf3540f9aee687900b7389d82c2c4dceb1dabb20ac68
Timestamp: 1746692915 Timestamp [UCT]: 2025-05-08 08:28:35 Age [y:d:h:m:s]: 00:245:22:16:17
Block: 1278326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173545 RingCT/type: yes/0
Extra: 01e51605cdff15ebe082d5cf3540f9aee687900b7389d82c2c4dceb1dabb20ac680211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd27e0e295e18e4b678193644ae3dd76520d02a5cfaef1bdf9e530ebc7faa709 0.600000000000 1765691 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": 1278336, "vin": [ { "gen": { "height": 1278326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd27e0e295e18e4b678193644ae3dd76520d02a5cfaef1bdf9e530ebc7faa709" } } ], "extra": [ 1, 229, 22, 5, 205, 255, 21, 235, 224, 130, 213, 207, 53, 64, 249, 174, 230, 135, 144, 11, 115, 137, 216, 44, 44, 77, 206, 177, 218, 187, 32, 172, 104, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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