Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e42e4b93ca7c3e707cbe1eef0dca0ce876e483d74e1148bcf89dab05eb446b7

Tx prefix hash: 72ea72edc8966fa8337c39fc06ea3facf9718ca7a3d202b17fd32dd5abd880be
Tx public key: 539d80c06d76e8154f3f7e9197f5c210c808d0f191a8fcdb95ac4c68aa3af6c3
Timestamp: 1715051381 Timestamp [UCT]: 2024-05-07 03:09:41 Age [y:d:h:m:s]: 00:361:20:51:43
Block: 1016535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258675 RingCT/type: yes/0
Extra: 01539d80c06d76e8154f3f7e9197f5c210c808d0f191a8fcdb95ac4c68aa3af6c30211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e40a89e4737ee69b0abc6ef2a404382145bc60167a41f388268a7b1baef15077 0.600000000000 1480144 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": 1016545, "vin": [ { "gen": { "height": 1016535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e40a89e4737ee69b0abc6ef2a404382145bc60167a41f388268a7b1baef15077" } } ], "extra": [ 1, 83, 157, 128, 192, 109, 118, 232, 21, 79, 63, 126, 145, 151, 245, 194, 16, 200, 8, 208, 241, 145, 168, 252, 219, 149, 172, 76, 104, 170, 58, 246, 195, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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