Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef84e8b85f3b2debe747f9427fb97e35d2d387abdc876070d21acc4a7e624ce4

Tx prefix hash: cc61975954cef1e394cf3f572f9c7da48ddecd87d90670535090b1629393ebde
Tx public key: 7a55651fe35498d2543e75025ab3a5afe6493d71a1ae8a37a8fecb89b05fe5e9
Timestamp: 1702441846 Timestamp [UCT]: 2023-12-13 04:30:46 Age [y:d:h:m:s]: 01:151:09:15:47
Block: 912009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369337 RingCT/type: yes/0
Extra: 017a55651fe35498d2543e75025ab3a5afe6493d71a1ae8a37a8fecb89b05fe5e902110000000e33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fabba4301d02c28a106c2c069d9460dc120cb72aa0ea11a3a853829afaf2aa24 0.600000000000 1369227 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": 912019, "vin": [ { "gen": { "height": 912009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fabba4301d02c28a106c2c069d9460dc120cb72aa0ea11a3a853829afaf2aa24" } } ], "extra": [ 1, 122, 85, 101, 31, 227, 84, 152, 210, 84, 62, 117, 2, 90, 179, 165, 175, 230, 73, 61, 113, 161, 174, 138, 55, 168, 254, 203, 137, 176, 95, 229, 233, 2, 17, 0, 0, 0, 14, 51, 175, 153, 244, 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