Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8716354d5170f0761769d0c7e3d0ab6418c582df16fa0fc2362562bf5a877f9

Tx prefix hash: ed238b1958f188475194b26c5c7b93a24f4fad82dba7c79ce6b1f6ce0288477e
Tx public key: fd9f293db7f3b1fc62fdd990997cba2f02afadc87f89dd59c1a43732ec72d9d7
Timestamp: 1751443017 Timestamp [UCT]: 2025-07-02 07:56:57 Age [y:d:h:m:s]: 00:130:14:07:30
Block: 1317101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91556 RingCT/type: yes/0
Extra: 01fd9f293db7f3b1fc62fdd990997cba2f02afadc87f89dd59c1a43732ec72d9d702110000000ebf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdb331a156d1cc1ac69feacba68b8158d369fda8a2342ef05ad150bf7a49b456 0.600000000000 1804766 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": 1317111, "vin": [ { "gen": { "height": 1317101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdb331a156d1cc1ac69feacba68b8158d369fda8a2342ef05ad150bf7a49b456" } } ], "extra": [ 1, 253, 159, 41, 61, 183, 243, 177, 252, 98, 253, 217, 144, 153, 124, 186, 47, 2, 175, 173, 200, 127, 137, 221, 89, 193, 164, 55, 50, 236, 114, 217, 215, 2, 17, 0, 0, 0, 14, 191, 81, 178, 162, 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