Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30ca633b86785d0736298db7acc867f978a5fa590b7a09f54fe0d30f717d98c5

Tx prefix hash: 765c3c20c737d08bc1c5f696f7aa7e605cd7ccac2c74277f468ae1564e8594ca
Tx public key: 0191a4a4b94c98260768aec87cb7f09b72dd45ce8ab639925cde736e0e6c140d
Timestamp: 1705081728 Timestamp [UCT]: 2024-01-12 17:48:48 Age [y:d:h:m:s]: 01:000:02:10:01
Block: 933856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261381 RingCT/type: yes/0
Extra: 010191a4a4b94c98260768aec87cb7f09b72dd45ce8ab639925cde736e0e6c140d0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abe3678b2ca0d4678e1c85c331cfef92aa32c5b2f68a39915cedd7477c3e60d9 0.600000000000 1391840 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": 933866, "vin": [ { "gen": { "height": 933856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abe3678b2ca0d4678e1c85c331cfef92aa32c5b2f68a39915cedd7477c3e60d9" } } ], "extra": [ 1, 1, 145, 164, 164, 185, 76, 152, 38, 7, 104, 174, 200, 124, 183, 240, 155, 114, 221, 69, 206, 138, 182, 57, 146, 92, 222, 115, 110, 14, 108, 20, 13, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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