Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 546ce6c4c5e817c856096451c506ba6ab267027179db86c404447fb15a9da01d

Tx prefix hash: f26618c23b6f7fa8633ed88c1818a725a096e4797013b2537b1aead3feee3e8d
Tx public key: b4dc762eaffd5ad78263f875220be189971bfe2e3ef19780b35dda8b926b5e5c
Timestamp: 1719113205 Timestamp [UCT]: 2024-06-23 03:26:45 Age [y:d:h:m:s]: 00:297:19:06:06
Block: 1050186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212816 RingCT/type: yes/0
Extra: 01b4dc762eaffd5ad78263f875220be189971bfe2e3ef19780b35dda8b926b5e5c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dc6887d899eca25e9cc0b6c7581b5c735d0cafc6d5753ea9024823665da1bc1 0.600000000000 1520347 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": 1050196, "vin": [ { "gen": { "height": 1050186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dc6887d899eca25e9cc0b6c7581b5c735d0cafc6d5753ea9024823665da1bc1" } } ], "extra": [ 1, 180, 220, 118, 46, 175, 253, 90, 215, 130, 99, 248, 117, 34, 11, 225, 137, 151, 27, 254, 46, 62, 241, 151, 128, 179, 93, 218, 139, 146, 107, 94, 92, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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