Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73530a66b8a4b4c1c03b152795bfcd6bd558ec37eec3712a84a0eddb97cd8d63

Tx prefix hash: 800c5cec23a7c28cb29afb4734cf889a931cffcd115f51589626d144a7642bb4
Tx public key: c74099c9e9acebcc17021e2ea43fd0d9a3fe3ad48393b6eef6353b69a488fd7b
Timestamp: 1722685759 Timestamp [UCT]: 2024-08-03 11:49:19 Age [y:d:h:m:s]: 01:066:14:00:31
Block: 1079820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306024 RingCT/type: yes/0
Extra: 01c74099c9e9acebcc17021e2ea43fd0d9a3fe3ad48393b6eef6353b69a488fd7b02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6747763fd6f1b4197627ac2fe701a6bbfc173aa7d2bceee58bee361407335264 0.600000000000 1552941 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": 1079830, "vin": [ { "gen": { "height": 1079820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6747763fd6f1b4197627ac2fe701a6bbfc173aa7d2bceee58bee361407335264" } } ], "extra": [ 1, 199, 64, 153, 201, 233, 172, 235, 204, 23, 2, 30, 46, 164, 63, 208, 217, 163, 254, 58, 212, 131, 147, 182, 238, 246, 53, 59, 105, 164, 136, 253, 123, 2, 17, 0, 0, 0, 5, 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