Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43ef61cd4052c9385566f4bec328ab0f3405cc2f176c9c472aad9136fcf6dcb2

Tx prefix hash: 92ea55fe8755b73ab64cd0643f97f282ac8ea76425037a716621ba49d0fafa5c
Tx public key: 0b26723f001a25c1f620f54d14f9c65f63d1a48a2f084819b631804e6f42e0ef
Timestamp: 1726958536 Timestamp [UCT]: 2024-09-21 22:42:16 Age [y:d:h:m:s]: 00:173:17:19:58
Block: 1115248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123984 RingCT/type: yes/0
Extra: 010b26723f001a25c1f620f54d14f9c65f63d1a48a2f084819b631804e6f42e0ef02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b568bc57723f5a27fcdcde85370c2934ceae18d11b5038b8ad4a144c0114486 0.600000000000 1595315 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": 1115258, "vin": [ { "gen": { "height": 1115248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b568bc57723f5a27fcdcde85370c2934ceae18d11b5038b8ad4a144c0114486" } } ], "extra": [ 1, 11, 38, 114, 63, 0, 26, 37, 193, 246, 32, 245, 77, 20, 249, 198, 95, 99, 209, 164, 138, 47, 8, 72, 25, 182, 49, 128, 78, 111, 66, 224, 239, 2, 17, 0, 0, 0, 6, 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