Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2290d1c1532dd28c58ebb704cd4f34fdef9d7978ffecb08e99426fb4544d2a4

Tx prefix hash: ad0af1796f9f7a462b58d47ac908036ba8dbc52c1c9421d0d65e601cdeeaad7d
Tx public key: 4fb3a87ab5182ca607acc9f81cc921a7700a1395ea8c973049c99df3c222b14c
Timestamp: 1762086447 Timestamp [UCT]: 2025-11-02 12:27:27 Age [y:d:h:m:s]: 00:049:12:03:43
Block: 1403346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35450 RingCT/type: yes/0
Extra: 014fb3a87ab5182ca607acc9f81cc921a7700a1395ea8c973049c99df3c222b14c02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab7cd32a0144150d9e03d1e765d8f55464ed15ed69bf8d2d9e833a1fbd589412 0.600000000000 1891685 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": 1403356, "vin": [ { "gen": { "height": 1403346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab7cd32a0144150d9e03d1e765d8f55464ed15ed69bf8d2d9e833a1fbd589412" } } ], "extra": [ 1, 79, 179, 168, 122, 181, 24, 44, 166, 7, 172, 201, 248, 28, 201, 33, 167, 112, 10, 19, 149, 234, 140, 151, 48, 73, 201, 157, 243, 194, 34, 177, 76, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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