Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30f917d46d436391f0ac185520f846bbb76fcf541f2bee9e2d5178c486426d13

Tx prefix hash: 46934a43c73962d8131a389f2c0de54bdc32d4438bd68c4943232a8cb2e83612
Tx public key: c8688ead18f296d27be8c36004b6d8839e6754565c67845f5a3c48267800e0c5
Timestamp: 1707517669 Timestamp [UCT]: 2024-02-09 22:27:49 Age [y:d:h:m:s]: 01:043:19:11:38
Block: 954059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292347 RingCT/type: yes/0
Extra: 01c8688ead18f296d27be8c36004b6d8839e6754565c67845f5a3c48267800e0c50211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd387ca2e02ce4570b30c1d0b064bc680c6976cda5a8bc2c3f12d7143b11a40d 0.600000000000 1413331 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": 954069, "vin": [ { "gen": { "height": 954059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd387ca2e02ce4570b30c1d0b064bc680c6976cda5a8bc2c3f12d7143b11a40d" } } ], "extra": [ 1, 200, 104, 142, 173, 24, 242, 150, 210, 123, 232, 195, 96, 4, 182, 216, 131, 158, 103, 84, 86, 92, 103, 132, 95, 90, 60, 72, 38, 120, 0, 224, 197, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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