Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b33e1e548a59b3e796e70897193a167569f734df3d3bd2cb047624f3ffda7397

Tx prefix hash: 071ff16cb073818bf4d063d141175b4d1b2bd5970832e204359dd2f4f5f29acf
Tx public key: 5fa7bd48053a57861d4a3995c600ae1ebe3ae32705865a05e64acf6c822e7f7d
Timestamp: 1711077694 Timestamp [UCT]: 2024-03-22 03:21:34 Age [y:d:h:m:s]: 01:035:08:46:45
Block: 983606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286253 RingCT/type: yes/0
Extra: 015fa7bd48053a57861d4a3995c600ae1ebe3ae32705865a05e64acf6c822e7f7d02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd0c450368e163e0f63b61113fa343e59c3f7517687eafdcaf727b5edbe85967 0.600000000000 1443747 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": 983616, "vin": [ { "gen": { "height": 983606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd0c450368e163e0f63b61113fa343e59c3f7517687eafdcaf727b5edbe85967" } } ], "extra": [ 1, 95, 167, 189, 72, 5, 58, 87, 134, 29, 74, 57, 149, 198, 0, 174, 30, 190, 58, 227, 39, 5, 134, 90, 5, 230, 74, 207, 108, 130, 46, 127, 125, 2, 17, 0, 0, 0, 7, 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