Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 771d5d6abcaef9a24f0c26ff3bf44be13b56f966b3c168b570acdf821c6b9f18

Tx prefix hash: 5f9f0a9aa7ab367884cb0ad18f1bfefc9490119126c7e41b88d5cafdeb6dc5aa
Tx public key: b1da2f3b36b7490757883c2ab843e258e8175dbfa7d0c13cc5e3daef52614581
Timestamp: 1736353723 Timestamp [UCT]: 2025-01-08 16:28:43 Age [y:d:h:m:s]: 00:086:13:20:16
Block: 1192996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61643 RingCT/type: yes/0
Extra: 01b1da2f3b36b7490757883c2ab843e258e8175dbfa7d0c13cc5e3daef526145810211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28bb4c1e5adbac53f9cd2a14cc8b9313d2f7c3fa2b0eb5a775ec7d2b8c6267e9 0.600000000000 1679553 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": 1193006, "vin": [ { "gen": { "height": 1192996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28bb4c1e5adbac53f9cd2a14cc8b9313d2f7c3fa2b0eb5a775ec7d2b8c6267e9" } } ], "extra": [ 1, 177, 218, 47, 59, 54, 183, 73, 7, 87, 136, 60, 42, 184, 67, 226, 88, 232, 23, 93, 191, 167, 208, 193, 60, 197, 227, 218, 239, 82, 97, 69, 129, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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