Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc748223ffa627eb1f0407deb373a9de40179a822771040bbd9239c9a6a20f34

Tx prefix hash: 6d34e5b207398bfc481a416d382b66c146b31123c4017313ab81e82784c867ee
Tx public key: a0a6d089118f09f5a84b05011fa234f59f28c1239939cbf0c147f37a0170d1e4
Timestamp: 1718474739 Timestamp [UCT]: 2024-06-15 18:05:39 Age [y:d:h:m:s]: 00:326:13:36:31
Block: 1044920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233380 RingCT/type: yes/0
Extra: 01a0a6d089118f09f5a84b05011fa234f59f28c1239939cbf0c147f37a0170d1e402110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35ea44a7b15f7a3e52485e9c9b419a59881c7394f9be0090740c69f7e50babb1 0.600000000000 1514357 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": 1044930, "vin": [ { "gen": { "height": 1044920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35ea44a7b15f7a3e52485e9c9b419a59881c7394f9be0090740c69f7e50babb1" } } ], "extra": [ 1, 160, 166, 208, 137, 17, 143, 9, 245, 168, 75, 5, 1, 31, 162, 52, 245, 159, 40, 193, 35, 153, 57, 203, 240, 193, 71, 243, 122, 1, 112, 209, 228, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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