Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc48426673b7371072bfd8eba04945f38cc2a09bbf9c743fc33989cd13b3ac3b

Tx prefix hash: 15297cbb790c2ee0baa10e50a6ae5654ab7f50e60efbd574b4c9314220f534d2
Tx public key: 72e4cdb01c15f7427bcb6aa49a4a6d1ff5a994e537d3e4fa7a8632c487b0c7e1
Timestamp: 1709873423 Timestamp [UCT]: 2024-03-08 04:50:23 Age [y:d:h:m:s]: 01:069:21:56:12
Block: 973604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310991 RingCT/type: yes/0
Extra: 0172e4cdb01c15f7427bcb6aa49a4a6d1ff5a994e537d3e4fa7a8632c487b0c7e102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a1df0d67bea0c2df12bc50f8511c15fa7861e96cdba1d31a7f47cdb172ff0f0 0.600000000000 1433539 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": 973614, "vin": [ { "gen": { "height": 973604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a1df0d67bea0c2df12bc50f8511c15fa7861e96cdba1d31a7f47cdb172ff0f0" } } ], "extra": [ 1, 114, 228, 205, 176, 28, 21, 247, 66, 123, 203, 106, 164, 154, 74, 109, 31, 245, 169, 148, 229, 55, 211, 228, 250, 122, 134, 50, 196, 135, 176, 199, 225, 2, 17, 0, 0, 0, 1, 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