Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd5ccf361bdf95399082f94a97458d66dd70fd14b0528b4f4cda8dc62ab02881

Tx prefix hash: fa7991ca0797a60a3d4194d8a8079707aa3af75ab18923d38b8991b42c81f97c
Tx public key: 7bc289829f3e3a4a487a9daba4306c1366abbee1d12df20008ab33e584c3c006
Timestamp: 1762045413 Timestamp [UCT]: 2025-11-02 01:03:33 Age [y:d:h:m:s]: 00:004:00:46:30
Block: 1403008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2873 RingCT/type: yes/0
Extra: 017bc289829f3e3a4a487a9daba4306c1366abbee1d12df20008ab33e584c3c006021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71d05948f3215f7ccb4f0d4f323c355690a81ba1df459fd9da9a5709e2c5ad91 0.600000000000 1891335 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": 1403018, "vin": [ { "gen": { "height": 1403008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71d05948f3215f7ccb4f0d4f323c355690a81ba1df459fd9da9a5709e2c5ad91" } } ], "extra": [ 1, 123, 194, 137, 130, 159, 62, 58, 74, 72, 122, 157, 171, 164, 48, 108, 19, 102, 171, 190, 225, 209, 45, 242, 0, 8, 171, 51, 229, 132, 195, 192, 6, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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