Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13a7a4ebf8823f2102b572375f2c96fe3c5a6ed642029bc2a6142b27d2960942

Tx prefix hash: 6073e6cf522762f258c5aac2b9b2d6a22ffde89e50ffd943a9bc072cdb6a602b
Tx public key: 03e2efeafc2f83748068659b353e8bfbdd650a1fde6a38a87732477fc5f36435
Timestamp: 1760161819 Timestamp [UCT]: 2025-10-11 05:50:19 Age [y:d:h:m:s]: 00:030:01:47:20
Block: 1387398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21539 RingCT/type: yes/0
Extra: 0103e2efeafc2f83748068659b353e8bfbdd650a1fde6a38a87732477fc5f36435021100000007a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a61e7cecc6625d7f2d9a7214ddb493c89df43b5ea69b60bebe6f6cc5ae6d461 0.600000000000 1875585 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": 1387408, "vin": [ { "gen": { "height": 1387398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a61e7cecc6625d7f2d9a7214ddb493c89df43b5ea69b60bebe6f6cc5ae6d461" } } ], "extra": [ 1, 3, 226, 239, 234, 252, 47, 131, 116, 128, 104, 101, 155, 53, 62, 139, 251, 221, 101, 10, 31, 222, 106, 56, 168, 119, 50, 71, 127, 197, 243, 100, 53, 2, 17, 0, 0, 0, 7, 165, 220, 205, 121, 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