Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75c1479bad4ce71ba18bf2f13a9cea57aa7f05aa90dc5b17aedee1ce08317cd9

Tx prefix hash: 60d976c41427f41b67590691cc05294ec7b8a50a97a2558a87725c449c435f46
Tx public key: d391e9464ab73ff7fc5b96955d4645e78bf6d2b2eaa40c75f26c93ed8ad1caff
Timestamp: 1713904698 Timestamp [UCT]: 2024-04-23 20:38:18 Age [y:d:h:m:s]: 00:358:17:46:15
Block: 1007023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256449 RingCT/type: yes/0
Extra: 01d391e9464ab73ff7fc5b96955d4645e78bf6d2b2eaa40c75f26c93ed8ad1caff0211000000117a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38845707d6b157b0fe854071468a043d7ba0361fb9e806cb6b7adcf15f669498 0.600000000000 1468237 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": 1007033, "vin": [ { "gen": { "height": 1007023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38845707d6b157b0fe854071468a043d7ba0361fb9e806cb6b7adcf15f669498" } } ], "extra": [ 1, 211, 145, 233, 70, 74, 183, 63, 247, 252, 91, 150, 149, 93, 70, 69, 231, 139, 246, 210, 178, 234, 164, 12, 117, 242, 108, 147, 237, 138, 209, 202, 255, 2, 17, 0, 0, 0, 17, 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