Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0d08402ff57425c32f46531c5ea1283af5a02ea36520fd757c614c487d06eee

Tx prefix hash: 2dab2446b76d5da226693d03a1c2e786175fd2d9873397d60594d6f03c4d2a1e
Tx public key: 4f571a13003d59e58f7cf99bb467d61e2f93baf0307d603b211c0074e0f25fc4
Timestamp: 1754444033 Timestamp [UCT]: 2025-08-06 01:33:53 Age [y:d:h:m:s]: 00:015:17:07:20
Block: 1341155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10295 RingCT/type: yes/0
Extra: 014f571a13003d59e58f7cf99bb467d61e2f93baf0307d603b211c0074e0f25fc40211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5f85b8a05c0069ecfd6fc819c56e39e7781f8056afbf792a364d065eaa03210 0.600000000000 1828978 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": 1341165, "vin": [ { "gen": { "height": 1341155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5f85b8a05c0069ecfd6fc819c56e39e7781f8056afbf792a364d065eaa03210" } } ], "extra": [ 1, 79, 87, 26, 19, 0, 61, 89, 229, 143, 124, 249, 155, 180, 103, 214, 30, 47, 147, 186, 240, 48, 125, 96, 59, 33, 28, 0, 116, 224, 242, 95, 196, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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