Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c87408926c9f3faac3620f2e5b941d124dc1b30c6e3513af348849393cff2e5a

Tx prefix hash: be1a2458bd08d44732d84d752ade10e78fd43a986ab0217dc908b9495b19c9af
Tx public key: bdbe55c31f4f6bf689930f89d03736a38fd3fdcecfa450d7a37d171a54015de9
Timestamp: 1740300149 Timestamp [UCT]: 2025-02-23 08:42:29 Age [y:d:h:m:s]: 00:226:23:03:50
Block: 1225379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159924 RingCT/type: yes/0
Extra: 01bdbe55c31f4f6bf689930f89d03736a38fd3fdcecfa450d7a37d171a54015de9021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f04711ef9220b7f265d4511741b04d7e788c0e49155affb383008f029b7302a1 0.600000000000 1712244 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": 1225389, "vin": [ { "gen": { "height": 1225379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f04711ef9220b7f265d4511741b04d7e788c0e49155affb383008f029b7302a1" } } ], "extra": [ 1, 189, 190, 85, 195, 31, 79, 107, 246, 137, 147, 15, 137, 208, 55, 54, 163, 143, 211, 253, 206, 207, 164, 80, 215, 163, 125, 23, 26, 84, 1, 93, 233, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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