Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdf20a31ae1fb3f0dd01b532519efb588b64deb72682448d614606e5630c1802

Tx prefix hash: 2a90ef4d1d3c93f6858456a889a1b89180e5e52f142840af2af82580caa5e8e4
Tx public key: 4e68ff445c6d761176100227ccb8acde2bedb26c86f4fb2facbfb8658d6fb9c8
Timestamp: 1745706204 Timestamp [UCT]: 2025-04-26 22:23:24 Age [y:d:h:m:s]: 00:206:11:14:53
Block: 1270162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145270 RingCT/type: yes/0
Extra: 014e68ff445c6d761176100227ccb8acde2bedb26c86f4fb2facbfb8658d6fb9c8021100000004f7011ad5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3b50ab41e09400cfb181459cda93e3fd55e8322fecf14be239fa23e227dea59 0.600000000000 1757403 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": 1270172, "vin": [ { "gen": { "height": 1270162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3b50ab41e09400cfb181459cda93e3fd55e8322fecf14be239fa23e227dea59" } } ], "extra": [ 1, 78, 104, 255, 68, 92, 109, 118, 17, 118, 16, 2, 39, 204, 184, 172, 222, 43, 237, 178, 108, 134, 244, 251, 47, 172, 191, 184, 101, 141, 111, 185, 200, 2, 17, 0, 0, 0, 4, 247, 1, 26, 213, 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