Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5675176e245c4a7e37bb43a2d6e5899ce253cbab70f71b0e7b3940d3b3976058

Tx prefix hash: 71a1112e81828448297685d9227f0aaab32c316a8ccfc940e09fd70d0d61b685
Tx public key: fab5e8e2772a3acbd1b93a582218ae71e21f918676251c1e8954c9a4bcc68d1d
Timestamp: 1723405900 Timestamp [UCT]: 2024-08-11 19:51:40 Age [y:d:h:m:s]: 00:276:03:04:06
Block: 1085787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197267 RingCT/type: yes/0
Extra: 01fab5e8e2772a3acbd1b93a582218ae71e21f918676251c1e8954c9a4bcc68d1d021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7003e51a47edd1c2dfdedd6507a979bf20609e458e05283961b474c34fe336d2 0.600000000000 1560376 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": 1085797, "vin": [ { "gen": { "height": 1085787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7003e51a47edd1c2dfdedd6507a979bf20609e458e05283961b474c34fe336d2" } } ], "extra": [ 1, 250, 181, 232, 226, 119, 42, 58, 203, 209, 185, 58, 88, 34, 24, 174, 113, 226, 31, 145, 134, 118, 37, 28, 30, 137, 84, 201, 164, 188, 198, 141, 29, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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