Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b47abe03c87431017bdb3a95a9e5391508515bcfca236579896f900014f5fe4

Tx prefix hash: 17e8e0b9c6b0f6c5ddb8bfa7ebf4ef3c0f88004dc3759e1c015ea2cc9ef302b6
Tx public key: 98fbb8afee7ef54627530c611e1e4d70f164f5598a3fc586e562ae6b3fa8d0c8
Timestamp: 1696101925 Timestamp [UCT]: 2023-09-30 19:25:25 Age [y:d:h:m:s]: 02:044:16:41:31
Block: 859630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551588 RingCT/type: yes/0
Extra: 0198fbb8afee7ef54627530c611e1e4d70f164f5598a3fc586e562ae6b3fa8d0c802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.870340119000 dcy

stealth address amount amount idx
00: 2945fd23abe2659afc30351f984594fb42ecfaa0961239618acbce27c9c90743 0.870340119000 1313864 of 0

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": 859640, "vin": [ { "gen": { "height": 859630 } } ], "vout": [ { "amount": 870340119, "target": { "key": "2945fd23abe2659afc30351f984594fb42ecfaa0961239618acbce27c9c90743" } } ], "extra": [ 1, 152, 251, 184, 175, 238, 126, 245, 70, 39, 83, 12, 97, 30, 30, 77, 112, 241, 100, 245, 89, 138, 63, 197, 134, 229, 98, 174, 107, 63, 168, 208, 200, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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