Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 462ee81afe42ffbf58204ff02c9fab3360de0ab441e7d46a8e7823fb1bf2a223

Tx prefix hash: 8fc7049d7c7e6547237d5f11c341555a453d5b2c901aacb0163581af3c0f6f76
Tx public key: c0a3df3b009d4d8415b3b31ff70c8fe70ee5d8730da3c6a7dca66eaa76f59954
Timestamp: 1634999537 Timestamp [UCT]: 2021-10-23 14:32:17 Age [y:d:h:m:s]: 03:083:09:38:37
Block: 358864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 837940 RingCT/type: yes/0
Extra: 01c0a3df3b009d4d8415b3b31ff70c8fe70ee5d8730da3c6a7dca66eaa76f5995402110000000af60c5d7e000000000000000000

1 output(s) for total of 39.713211351000 dcy

stealth address amount amount idx
00: 3167e1098260a0d6954ea986529ac0b2c0136810debcb83e7ad55248dd70c7b1 39.713211351000 731029 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": 358874, "vin": [ { "gen": { "height": 358864 } } ], "vout": [ { "amount": 39713211351, "target": { "key": "3167e1098260a0d6954ea986529ac0b2c0136810debcb83e7ad55248dd70c7b1" } } ], "extra": [ 1, 192, 163, 223, 59, 0, 157, 77, 132, 21, 179, 179, 31, 247, 12, 143, 231, 14, 229, 216, 115, 13, 163, 198, 167, 220, 166, 110, 170, 118, 245, 153, 84, 2, 17, 0, 0, 0, 10, 246, 12, 93, 126, 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