Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f103a78e0bfed59bb094ddeff8b29877d918a42c4aa747d024d66df77e95179

Tx prefix hash: 5164150eb9b43016e318fa447d1b4b4b4377047941e7c5f9bb00db5986036734
Tx public key: 0af1c79506268926d0528bcd1f7a9ca36555c27cb364a6edeaa3e72be4817e0f
Timestamp: 1730446836 Timestamp [UCT]: 2024-11-01 07:40:36 Age [y:d:h:m:s]: 00:140:10:17:34
Block: 1144087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100192 RingCT/type: yes/0
Extra: 010af1c79506268926d0528bcd1f7a9ca36555c27cb364a6edeaa3e72be4817e0f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ec9ddaca07f7a7ab7eebb7dcc21e0a7b7bc412123e1dc56e251c40ebbcf2841 0.600000000000 1628174 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": 1144097, "vin": [ { "gen": { "height": 1144087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ec9ddaca07f7a7ab7eebb7dcc21e0a7b7bc412123e1dc56e251c40ebbcf2841" } } ], "extra": [ 1, 10, 241, 199, 149, 6, 38, 137, 38, 208, 82, 139, 205, 31, 122, 156, 163, 101, 85, 194, 124, 179, 100, 166, 237, 234, 163, 231, 43, 228, 129, 126, 15, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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