Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edb2e3a5d2cbf8672cbb3591712a8180c4682b479ae2e0aa30badcf2fab76160

Tx prefix hash: 15c3ef85f83cd81b9f0fcd4d62ce72f0bd5183814d2fc47024c1096f4a882dbc
Tx public key: 2edd99f531ed713399e2d3f258454b6c1d9ac185da293b269ec9cfed1262e8f0
Timestamp: 1738362405 Timestamp [UCT]: 2025-01-31 22:26:45 Age [y:d:h:m:s]: 00:294:01:59:56
Block: 1209366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207941 RingCT/type: yes/0
Extra: 012edd99f531ed713399e2d3f258454b6c1d9ac185da293b269ec9cfed1262e8f0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9ddbf96102745db4774a3f605b4e3d44aece186d3bcb77f80c31236860b1561 0.600000000000 1696107 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": 1209376, "vin": [ { "gen": { "height": 1209366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9ddbf96102745db4774a3f605b4e3d44aece186d3bcb77f80c31236860b1561" } } ], "extra": [ 1, 46, 221, 153, 245, 49, 237, 113, 51, 153, 226, 211, 242, 88, 69, 75, 108, 29, 154, 193, 133, 218, 41, 59, 38, 158, 201, 207, 237, 18, 98, 232, 240, 2, 17, 0, 0, 0, 3, 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