Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9981b11fdd1a946aba10771feb207f94a3ee88073b03699d141b7f5e9315ad6c

Tx prefix hash: c8b39395d06ebc67e01a60ff054495242ce2b285af78685c3b192f91e0b313e7
Tx public key: 569cb6321ae5fd652ca32f360f3d06f91e5da63c6db8d80d1c18c2854480a2fe
Timestamp: 1735871543 Timestamp [UCT]: 2025-01-03 02:32:23 Age [y:d:h:m:s]: 00:352:21:58:47
Block: 1189007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249789 RingCT/type: yes/0
Extra: 01569cb6321ae5fd652ca32f360f3d06f91e5da63c6db8d80d1c18c2854480a2fe021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5866d71cd65911660101bcdf10be053da89d0a05815d1a0a2914cc6e72e7c47e 0.600000000000 1675512 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": 1189017, "vin": [ { "gen": { "height": 1189007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5866d71cd65911660101bcdf10be053da89d0a05815d1a0a2914cc6e72e7c47e" } } ], "extra": [ 1, 86, 156, 182, 50, 26, 229, 253, 101, 44, 163, 47, 54, 15, 61, 6, 249, 30, 93, 166, 60, 109, 184, 216, 13, 28, 24, 194, 133, 68, 128, 162, 254, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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