Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23eacb11857ed29ae0257f1adcd123eebb2f2d9f721c0f8c56dc7a7c84d06d56

Tx prefix hash: 8c783e16da2d97a6a61e33d432960efc7c7e099ea5e357b2f808ccb4767eb1ec
Tx public key: 5052cee9b5d855a5e654f98c6cc5745934b3bea07b9565d9ed508a0fd7a70b1d
Timestamp: 1715975230 Timestamp [UCT]: 2024-05-17 19:47:10 Age [y:d:h:m:s]: 00:320:17:57:32
Block: 1024191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229256 RingCT/type: yes/0
Extra: 015052cee9b5d855a5e654f98c6cc5745934b3bea07b9565d9ed508a0fd7a70b1d021100000006c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5281c43f5495d70f5a95b0858ffd6dbbc44d825773552d43ffa470784d127064 0.600000000000 1489742 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": 1024201, "vin": [ { "gen": { "height": 1024191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5281c43f5495d70f5a95b0858ffd6dbbc44d825773552d43ffa470784d127064" } } ], "extra": [ 1, 80, 82, 206, 233, 181, 216, 85, 165, 230, 84, 249, 140, 108, 197, 116, 89, 52, 179, 190, 160, 123, 149, 101, 217, 237, 80, 138, 15, 215, 167, 11, 29, 2, 17, 0, 0, 0, 6, 197, 69, 41, 96, 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