Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3238ec36ac125dc6e655f8f19655e2219ba42669ff56bbafb89cf6168e066ace

Tx prefix hash: b22946b39d2e395a79f7fde6f1f3e70d6576087ef179966ea4310ad38af5cfaa
Tx public key: a40d77952e6dfd2f7ab8f38c44cfa0795dcb6a459562d948fd9aa6a15b0e09ea
Timestamp: 1697166843 Timestamp [UCT]: 2023-10-13 03:14:03 Age [y:d:h:m:s]: 01:173:17:55:24
Block: 868451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385211 RingCT/type: yes/0
Extra: 01a40d77952e6dfd2f7ab8f38c44cfa0795dcb6a459562d948fd9aa6a15b0e09ea02110000000133af99f4000000000000000000

1 output(s) for total of 0.813694453000 dcy

stealth address amount amount idx
00: f290f647868869cd74001f404f453612ee37a95d379af21041449808d5340422 0.813694453000 1323262 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": 868461, "vin": [ { "gen": { "height": 868451 } } ], "vout": [ { "amount": 813694453, "target": { "key": "f290f647868869cd74001f404f453612ee37a95d379af21041449808d5340422" } } ], "extra": [ 1, 164, 13, 119, 149, 46, 109, 253, 47, 122, 184, 243, 140, 68, 207, 160, 121, 93, 203, 106, 69, 149, 98, 217, 72, 253, 154, 166, 161, 91, 14, 9, 234, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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