Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89c729968f2d1204c7e45dce7fdb1f9c3ed1a3ca14889d1f118bd4eaa1bd4072

Tx prefix hash: ec4ee44e49cc45540ed87bc7a13a1b45d54aef5819a69ce51e272dffdb4e3926
Tx public key: 37c1424bad94177e637d3a5750325ba5d22416bfdcdd771d21a5c0dcce909b2d
Timestamp: 1746128570 Timestamp [UCT]: 2025-05-01 19:42:50 Age [y:d:h:m:s]: 00:198:03:38:03
Block: 1273652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139334 RingCT/type: yes/0
Extra: 0137c1424bad94177e637d3a5750325ba5d22416bfdcdd771d21a5c0dcce909b2d021100000005d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 507565b01fc37bedc5601e1d59402102dbc2cfe3e3561ae3076c6a75d3edaae9 0.600000000000 1760935 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": 1273662, "vin": [ { "gen": { "height": 1273652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "507565b01fc37bedc5601e1d59402102dbc2cfe3e3561ae3076c6a75d3edaae9" } } ], "extra": [ 1, 55, 193, 66, 75, 173, 148, 23, 126, 99, 125, 58, 87, 80, 50, 91, 165, 210, 36, 22, 191, 220, 221, 119, 29, 33, 165, 192, 220, 206, 144, 155, 45, 2, 17, 0, 0, 0, 5, 216, 231, 210, 65, 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