Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e3300053c3fc6f74b095c4edb5380329f9bde154690a11e962191ab93736ded

Tx prefix hash: 348766685b1b00eeddb5e7c1221122c2f59bf2d36d3ffa517e63d8d17c7f78c5
Tx public key: b355c6bcfbde406e0414b43068f71974c9c5e946b5ce435abc3a3a6ffb03f81b
Timestamp: 1757559222 Timestamp [UCT]: 2025-09-11 02:53:42 Age [y:d:h:m:s]: 00:141:02:31:31
Block: 1365836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100850 RingCT/type: yes/0
Extra: 01b355c6bcfbde406e0414b43068f71974c9c5e946b5ce435abc3a3a6ffb03f81b021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 004924ebd633914d7f80613d32224a0d65ff920a72bb448d6b22bf6d634240fb 0.600000000000 1853875 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": 1365846, "vin": [ { "gen": { "height": 1365836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "004924ebd633914d7f80613d32224a0d65ff920a72bb448d6b22bf6d634240fb" } } ], "extra": [ 1, 179, 85, 198, 188, 251, 222, 64, 110, 4, 20, 180, 48, 104, 247, 25, 116, 201, 197, 233, 70, 181, 206, 67, 90, 188, 58, 58, 111, 251, 3, 248, 27, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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