Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e256833e446310cd64af24a92c918e59df05ef6981f39dace2d6020232dcf47c

Tx prefix hash: e3076bbd9145fb12c9609078e0f7c7b874b43bd7193488b9a8af614a4e7cec9c
Tx public key: f44ed84044a185c32f3cc762a4953d8ce7d76ded94c2ed9f16a1399eaff3a6b6
Timestamp: 1762365009 Timestamp [UCT]: 2025-11-05 17:50:09 Age [y:d:h:m:s]: 00:008:10:55:49
Block: 1405652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6060 RingCT/type: yes/0
Extra: 01f44ed84044a185c32f3cc762a4953d8ce7d76ded94c2ed9f16a1399eaff3a6b60211000000055dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1b417366c50dfde70940a2dd1e657d21be5f9f86e91ea7e5fa0a4d6e3d3196f 0.600000000000 1894033 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": 1405662, "vin": [ { "gen": { "height": 1405652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1b417366c50dfde70940a2dd1e657d21be5f9f86e91ea7e5fa0a4d6e3d3196f" } } ], "extra": [ 1, 244, 78, 216, 64, 68, 161, 133, 195, 47, 60, 199, 98, 164, 149, 61, 140, 231, 215, 109, 237, 148, 194, 237, 159, 22, 161, 57, 158, 175, 243, 166, 182, 2, 17, 0, 0, 0, 5, 93, 251, 190, 42, 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