Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6079838b3a5ff479da7704cc36c084742559fdf4de0348671c4b79e23a2939dc

Tx prefix hash: 2b8903ced5e22ca8875bdbb5c8bf9d6d6d35f8c6bf1864ac63d044ed00d711b1
Tx public key: b42961a1e6bc9e83e2dbfc943c6d57709b5ef9665231462c2a11158d903a0a8e
Timestamp: 1697275567 Timestamp [UCT]: 2023-10-14 09:26:07 Age [y:d:h:m:s]: 01:098:01:58:04
Block: 869360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331319 RingCT/type: yes/0
Extra: 01b42961a1e6bc9e83e2dbfc943c6d57709b5ef9665231462c2a11158d903a0a8e02110000000133af99f4000000000000000000

1 output(s) for total of 0.808070886000 dcy

stealth address amount amount idx
00: 7c3285506fd70f24f877fc3b0c923f67e7f6f6b27d785c2dc99a3501f6c9ac7e 0.808070886000 1324205 of 0

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": 869370, "vin": [ { "gen": { "height": 869360 } } ], "vout": [ { "amount": 808070886, "target": { "key": "7c3285506fd70f24f877fc3b0c923f67e7f6f6b27d785c2dc99a3501f6c9ac7e" } } ], "extra": [ 1, 180, 41, 97, 161, 230, 188, 158, 131, 226, 219, 252, 148, 60, 109, 87, 112, 155, 94, 249, 102, 82, 49, 70, 44, 42, 17, 21, 141, 144, 58, 10, 142, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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