Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c1d4884cedb41d8cade37832f0e97d715d5e3d22cbde1c1e7e61a853d25e682

Tx prefix hash: 5aaf4d27f656db0cbfaad2db940897c651992de03adc33f3ee60fd6ea323121a
Tx public key: 4e3aa91d1a13a04ae4a90583cb21e5f47a64ca8007928ae6f36e306d2c297b4a
Timestamp: 1718842513 Timestamp [UCT]: 2024-06-20 00:15:13 Age [y:d:h:m:s]: 00:250:01:54:57
Block: 1047956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178656 RingCT/type: yes/0
Extra: 014e3aa91d1a13a04ae4a90583cb21e5f47a64ca8007928ae6f36e306d2c297b4a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ac395910e2fbc0d032dda1e4a8d1fa21cb7d626939beb4d77645649cac4f4e2 0.600000000000 1517915 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": 1047966, "vin": [ { "gen": { "height": 1047956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ac395910e2fbc0d032dda1e4a8d1fa21cb7d626939beb4d77645649cac4f4e2" } } ], "extra": [ 1, 78, 58, 169, 29, 26, 19, 160, 74, 228, 169, 5, 131, 203, 33, 229, 244, 122, 100, 202, 128, 7, 146, 138, 230, 243, 110, 48, 109, 44, 41, 123, 74, 2, 17, 0, 0, 0, 1, 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