Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fe0ae3f92008aa5b43b012c956fb2a5454be7ab5249999c01e71f7fc3d1ba6b

Tx prefix hash: dcbe7db06aa6496d74d67d1159d4faf43bf362eb42500b80f133c5ed33483d8c
Tx public key: e8640dbc5f6185150c643a99c288b79e9383c241f2c2b888aabe1944266c9277
Timestamp: 1760021257 Timestamp [UCT]: 2025-10-09 14:47:37 Age [y:d:h:m:s]: 00:028:07:29:02
Block: 1386230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20275 RingCT/type: yes/0
Extra: 01e8640dbc5f6185150c643a99c288b79e9383c241f2c2b888aabe1944266c927702110000000397baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c532ca3e8a3d0d4fbeb14f79d38d2df9e355656ed668d9abb0f8fb5e3616199 0.600000000000 1874395 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": 1386240, "vin": [ { "gen": { "height": 1386230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c532ca3e8a3d0d4fbeb14f79d38d2df9e355656ed668d9abb0f8fb5e3616199" } } ], "extra": [ 1, 232, 100, 13, 188, 95, 97, 133, 21, 12, 100, 58, 153, 194, 136, 183, 158, 147, 131, 194, 65, 242, 194, 184, 136, 170, 190, 25, 68, 38, 108, 146, 119, 2, 17, 0, 0, 0, 3, 151, 186, 249, 34, 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