Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01078d37c2894e672521c2013e03c43635f0f83df0310b31d9d20638502dbaca

Tx prefix hash: 71da46bee433fb96638a6cc0a1f88207e8a874696bc70d76a680a309c7f867fb
Tx public key: cda0479e47e65544cfb2e576db71b0ae72c4badf01879bdff7eca27fc1780f24
Timestamp: 1694323231 Timestamp [UCT]: 2023-09-10 05:20:31 Age [y:d:h:m:s]: 01:210:06:42:50
Block: 844866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411384 RingCT/type: yes/0
Extra: 01cda0479e47e65544cfb2e576db71b0ae72c4badf01879bdff7eca27fc1780f2402110000000e4b8f5122000000000000000000

1 output(s) for total of 0.974110637000 dcy

stealth address amount amount idx
00: 29f245b6822094c9b41c3b0e764c6f6961a6c0d94cee84b7706221c4ae9789b3 0.974110637000 1298202 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": 844876, "vin": [ { "gen": { "height": 844866 } } ], "vout": [ { "amount": 974110637, "target": { "key": "29f245b6822094c9b41c3b0e764c6f6961a6c0d94cee84b7706221c4ae9789b3" } } ], "extra": [ 1, 205, 160, 71, 158, 71, 230, 85, 68, 207, 178, 229, 118, 219, 113, 176, 174, 114, 196, 186, 223, 1, 135, 155, 223, 247, 236, 162, 127, 193, 120, 15, 36, 2, 17, 0, 0, 0, 14, 75, 143, 81, 34, 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