Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 673036a2a3eef6c4de84ac029394e288cfdcfc0238edba58b309d75c8838e0dd

Tx prefix hash: 93b025f23515842ec8b5735b61ed74110702bc97480d73fc99764460d2fb2097
Tx public key: df114c1d5b9983ab72794e99f8df71bc296442d827679aa8d11ae7802f8a2e49
Timestamp: 1577192662 Timestamp [UCT]: 2019-12-24 13:04:22 Age [y:d:h:m:s]: 04:338:10:23:59
Block: 30720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131009 RingCT/type: yes/0
Extra: 01df114c1d5b9983ab72794e99f8df71bc296442d827679aa8d11ae7802f8a2e490211000000fcc3a1a09f000000000000000000

1 output(s) for total of 485.542657698000 dcy

stealth address amount amount idx
00: 41668414bd3bd27f7d740d663970cdd69fe43f50951a735a5e83ea6f5468e223 485.542657698000 50716 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": 30730, "vin": [ { "gen": { "height": 30720 } } ], "vout": [ { "amount": 485542657698, "target": { "key": "41668414bd3bd27f7d740d663970cdd69fe43f50951a735a5e83ea6f5468e223" } } ], "extra": [ 1, 223, 17, 76, 29, 91, 153, 131, 171, 114, 121, 78, 153, 248, 223, 113, 188, 41, 100, 66, 216, 39, 103, 154, 168, 209, 26, 231, 128, 47, 138, 46, 73, 2, 17, 0, 0, 0, 252, 195, 161, 160, 159, 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