Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bac10fee92ac1a265153e4c212ea12b656ede4f08188ef37461cf363efa41b1

Tx prefix hash: 91f918199f4c59fffb10ee6fe2e92525a04e36a07d68aeb470a88c7e8b2d0297
Tx public key: a53a8fa45059843c331d3644016c710c3e8a5322749d5d98e0e5e7672db6fda6
Timestamp: 1745631238 Timestamp [UCT]: 2025-04-26 01:33:58 Age [y:d:h:m:s]: 00:198:20:25:38
Block: 1269517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139844 RingCT/type: yes/0
Extra: 01a53a8fa45059843c331d3644016c710c3e8a5322749d5d98e0e5e7672db6fda602110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 369bc1faf91d3397b92d99e3e2122e1a03b0bcfe18e814d8496225d546323884 0.600000000000 1756756 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": 1269527, "vin": [ { "gen": { "height": 1269517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "369bc1faf91d3397b92d99e3e2122e1a03b0bcfe18e814d8496225d546323884" } } ], "extra": [ 1, 165, 58, 143, 164, 80, 89, 132, 60, 51, 29, 54, 68, 1, 108, 113, 12, 62, 138, 83, 34, 116, 157, 93, 152, 224, 229, 231, 103, 45, 182, 253, 166, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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