Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5c6ba8908bca619bf7bc6fd8a6c5015a44618f8d23fdba8e031990db6000922

Tx prefix hash: f9d01bb0981ba0a6097c12dd199c608ce7cb40d4cfe118a3d2328ceab121534f
Tx public key: 6be1aa2d9eaad3881ab59b7fcc674474e7f76927e2283af1916a2e9efd6ec5a3
Timestamp: 1725991859 Timestamp [UCT]: 2024-09-10 18:10:59 Age [y:d:h:m:s]: 00:104:05:42:54
Block: 1107233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74550 RingCT/type: yes/0
Extra: 016be1aa2d9eaad3881ab59b7fcc674474e7f76927e2283af1916a2e9efd6ec5a302110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1222bd29ea4152c96f9c4f998c000e2a4626247599f5e919303024fb98714441 0.600000000000 1584840 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": 1107243, "vin": [ { "gen": { "height": 1107233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1222bd29ea4152c96f9c4f998c000e2a4626247599f5e919303024fb98714441" } } ], "extra": [ 1, 107, 225, 170, 45, 158, 170, 211, 136, 26, 181, 155, 127, 204, 103, 68, 116, 231, 247, 105, 39, 226, 40, 58, 241, 145, 106, 46, 158, 253, 110, 197, 163, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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