Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32b3de0a463f085ee247f00945921db797322eac1f269c8ae93357c9b47c6971

Tx prefix hash: b9ba7e4c4c4f9b098897fc41f86255532026f22902876effa666f79240ca6fcf
Tx public key: 058df9ce0a42faba0fae989026f6bb3c73a2881aa32ae1da4c1535e701930b16
Timestamp: 1657127261 Timestamp [UCT]: 2022-07-06 17:07:41 Age [y:d:h:m:s]: 02:265:08:29:09
Block: 538009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 710783 RingCT/type: yes/0
Extra: 01058df9ce0a42faba0fae989026f6bb3c73a2881aa32ae1da4c1535e701930b1602110000000d4da16a3a000000000000000000

1 output(s) for total of 10.124020006000 dcy

stealth address amount amount idx
00: e57c489b17c75d2645fbaa4a955e79ed3bb7b9ade15e47ce2dcf743f9f10c161 10.124020006000 967956 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": 538019, "vin": [ { "gen": { "height": 538009 } } ], "vout": [ { "amount": 10124020006, "target": { "key": "e57c489b17c75d2645fbaa4a955e79ed3bb7b9ade15e47ce2dcf743f9f10c161" } } ], "extra": [ 1, 5, 141, 249, 206, 10, 66, 250, 186, 15, 174, 152, 144, 38, 246, 187, 60, 115, 162, 136, 26, 163, 42, 225, 218, 76, 21, 53, 231, 1, 147, 11, 22, 2, 17, 0, 0, 0, 13, 77, 161, 106, 58, 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