Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6a028c77e4118cdba9103354adb448d242ad5aacb3d3d130f21cd0409a7264d

Tx prefix hash: bd38db1fe78660f6f28cb9e13e84fb38faecedfe4f6b114b01b86f46636c0cb6
Tx public key: dbd5f80aca9247762e047bb1f948af375b60dad4e876e43f6721bc48817bdd1a
Timestamp: 1748871063 Timestamp [UCT]: 2025-06-02 13:31:03 Age [y:d:h:m:s]: 00:165:11:01:48
Block: 1296377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115928 RingCT/type: yes/0
Extra: 01dbd5f80aca9247762e047bb1f948af375b60dad4e876e43f6721bc48817bdd1a021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b659068f30326c86fafc6c23abc8a10cff8b024dcd23334163a47b8aba8d040 0.600000000000 1783886 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": 1296387, "vin": [ { "gen": { "height": 1296377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b659068f30326c86fafc6c23abc8a10cff8b024dcd23334163a47b8aba8d040" } } ], "extra": [ 1, 219, 213, 248, 10, 202, 146, 71, 118, 46, 4, 123, 177, 249, 72, 175, 55, 91, 96, 218, 212, 232, 118, 228, 63, 103, 33, 188, 72, 129, 123, 221, 26, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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