Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23e098af28a274e713c13f6fd07786faac07e4b7c278f0b6eeb06aaeed55db95

Tx prefix hash: 55ab5f4557cb02869650d691e6d402a7712ab86ff2ed436022d85c87789a7144
Tx public key: e2d0c84158d0b8849cbad4672b6c9e5221f7b2f67e61474c48e76c80cf0e4265
Timestamp: 1724177420 Timestamp [UCT]: 2024-08-20 18:10:20 Age [y:d:h:m:s]: 00:252:15:09:19
Block: 1092196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180461 RingCT/type: yes/0
Extra: 01e2d0c84158d0b8849cbad4672b6c9e5221f7b2f67e61474c48e76c80cf0e4265021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 986a56e95757ce6c3c9939abcff370e9fd3052fd4939afda7cd708d4869d9479 0.600000000000 1566895 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": 1092206, "vin": [ { "gen": { "height": 1092196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "986a56e95757ce6c3c9939abcff370e9fd3052fd4939afda7cd708d4869d9479" } } ], "extra": [ 1, 226, 208, 200, 65, 88, 208, 184, 132, 156, 186, 212, 103, 43, 108, 158, 82, 33, 247, 178, 246, 126, 97, 71, 76, 72, 231, 108, 128, 207, 14, 66, 101, 2, 17, 0, 0, 0, 4, 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