Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60322c1bc4de1436a2c4e03fc3c3ec9272e5e7ab4bf8037658fcf52a892afc6e

Tx prefix hash: c61e490da5e8fdeaf8aa30dda3cad18840e31af9d2c353c5564c42e2e62650c0
Tx public key: 46697352ffcebd870d6f4e0c46e34e1960b3633f4b7fd670ae8487ab324fb452
Timestamp: 1708581446 Timestamp [UCT]: 2024-02-22 05:57:26 Age [y:d:h:m:s]: 01:303:06:04:36
Block: 962889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475531 RingCT/type: yes/0
Extra: 0146697352ffcebd870d6f4e0c46e34e1960b3633f4b7fd670ae8487ab324fb45202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0fd5b5e053339eb69b37b38c8bdbd2a9cfe4238047e245f88ddf2e8529ee91c 0.600000000000 1422576 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": 962899, "vin": [ { "gen": { "height": 962889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0fd5b5e053339eb69b37b38c8bdbd2a9cfe4238047e245f88ddf2e8529ee91c" } } ], "extra": [ 1, 70, 105, 115, 82, 255, 206, 189, 135, 13, 111, 78, 12, 70, 227, 78, 25, 96, 179, 99, 63, 75, 127, 214, 112, 174, 132, 135, 171, 50, 79, 180, 82, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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