Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df781c70bedfc89949cc65c88f85ddfa9bf0d7997dc9724caceb4207470b2f21

Tx prefix hash: f7d90991df3e005ffd138d6974cb1534aea4509ad0dfa37b178acbd3997cfc6c
Tx public key: 9dfae535a0072ccf5e1a224dbb3dea48fba5a0bf961131b2c8ad99b6454fd36e
Timestamp: 1716717296 Timestamp [UCT]: 2024-05-26 09:54:56 Age [y:d:h:m:s]: 00:318:18:36:55
Block: 1030354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227822 RingCT/type: yes/0
Extra: 019dfae535a0072ccf5e1a224dbb3dea48fba5a0bf961131b2c8ad99b6454fd36e0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88c76c4db3b5da1a7a0d306450f9259b3a9370d0746ff727f85bfcb7c2482f6d 0.600000000000 1498609 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": 1030364, "vin": [ { "gen": { "height": 1030354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88c76c4db3b5da1a7a0d306450f9259b3a9370d0746ff727f85bfcb7c2482f6d" } } ], "extra": [ 1, 157, 250, 229, 53, 160, 7, 44, 207, 94, 26, 34, 77, 187, 61, 234, 72, 251, 165, 160, 191, 150, 17, 49, 178, 200, 173, 153, 182, 69, 79, 211, 110, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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