Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46512232e64f9d4e9432f1f5b5bd009bdad7c719f33901f5ff5f542072a91f8d

Tx prefix hash: ba5250e628ce13d05dcf6d891de7db06d64bb34a646540fb6669e92f109d1cfd
Tx public key: a2f2e828d0db7b7e143e5a068b810e3d69bf7856fa00450045edafa577a55090
Timestamp: 1740638889 Timestamp [UCT]: 2025-02-27 06:48:09 Age [y:d:h:m:s]: 00:336:07:04:57
Block: 1228186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238029 RingCT/type: yes/0
Extra: 01a2f2e828d0db7b7e143e5a068b810e3d69bf7856fa00450045edafa577a5509002110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e4f2ae88329c88a65c8b9d04b6c3637e2220c8922ec0a823e6db33852f27932 0.600000000000 1715063 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": 1228196, "vin": [ { "gen": { "height": 1228186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e4f2ae88329c88a65c8b9d04b6c3637e2220c8922ec0a823e6db33852f27932" } } ], "extra": [ 1, 162, 242, 232, 40, 208, 219, 123, 126, 20, 62, 90, 6, 139, 129, 14, 61, 105, 191, 120, 86, 250, 0, 69, 0, 69, 237, 175, 165, 119, 165, 80, 144, 2, 17, 0, 0, 0, 15, 0, 127, 151, 138, 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