Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f725386b6204af3a21d8f9f84b54ddd3d651887cb2973b9805f0bb33939173e

Tx prefix hash: 21a4929fa4c91949823ab3da1993631ca081863a61b8a6f6b3fedf68f553283b
Tx public key: 87909791b75d8ccded0f8b2c0253be35d82cd7191a66ad1f4f6eb13804ae8fe7
Timestamp: 1738402232 Timestamp [UCT]: 2025-02-01 09:30:32 Age [y:d:h:m:s]: 00:293:02:58:05
Block: 1209693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207250 RingCT/type: yes/0
Extra: 0187909791b75d8ccded0f8b2c0253be35d82cd7191a66ad1f4f6eb13804ae8fe7021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a9d871bcc0dd9c359e6df9b580ac31e4777b3e3fb8aab21a16d5b0d7c22b343 0.600000000000 1696438 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": 1209703, "vin": [ { "gen": { "height": 1209693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a9d871bcc0dd9c359e6df9b580ac31e4777b3e3fb8aab21a16d5b0d7c22b343" } } ], "extra": [ 1, 135, 144, 151, 145, 183, 93, 140, 205, 237, 15, 139, 44, 2, 83, 190, 53, 216, 44, 215, 25, 26, 102, 173, 31, 79, 110, 177, 56, 4, 174, 143, 231, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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