Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84309974e334071d9c109d645aa5f3ed9f93b04278b47ec509e998d8fc8b28e9

Tx prefix hash: 34878b371fe6d76a298196cb3cd56b56456eafbede04c461ebabd10b1dfeb02e
Tx public key: 89246dc227aab2d57d58dc33b2436a2171f6a5aaf6df846d0f18b906caaef4b3
Timestamp: 1714078516 Timestamp [UCT]: 2024-04-25 20:55:16 Age [y:d:h:m:s]: 00:258:17:27:17
Block: 1008452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185201 RingCT/type: yes/0
Extra: 0189246dc227aab2d57d58dc33b2436a2171f6a5aaf6df846d0f18b906caaef4b302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f753957ef03b772a4090df38f0d5eaf55d9c3f9d97e21ec9c7662beb1d1c48a 0.600000000000 1469922 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": 1008462, "vin": [ { "gen": { "height": 1008452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f753957ef03b772a4090df38f0d5eaf55d9c3f9d97e21ec9c7662beb1d1c48a" } } ], "extra": [ 1, 137, 36, 109, 194, 39, 170, 178, 213, 125, 88, 220, 51, 178, 67, 106, 33, 113, 246, 165, 170, 246, 223, 132, 109, 15, 24, 185, 6, 202, 174, 244, 179, 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