Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7a47b01a0ff2ae568dc19a408e3cb168d8909d081bf04148a731fa8c0e763b9

Tx prefix hash: 26a6485c3a35120bc663e103ca62965af28d8dbe7a809998d9ee0ed05d8f058d
Tx public key: 0ce95322d95757609ddf652714dd7a63acc9dd560b0a012ee465ea2e4ec2ac78
Timestamp: 1732868223 Timestamp [UCT]: 2024-11-29 08:17:03 Age [y:d:h:m:s]: 00:115:09:14:06
Block: 1164140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82262 RingCT/type: yes/0
Extra: 010ce95322d95757609ddf652714dd7a63acc9dd560b0a012ee465ea2e4ec2ac78021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f017a3d2f2ce0e9127501b4628e5d9be4a48ec4a64b9dc696221cc98a7546616 0.600000000000 1649813 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": 1164150, "vin": [ { "gen": { "height": 1164140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f017a3d2f2ce0e9127501b4628e5d9be4a48ec4a64b9dc696221cc98a7546616" } } ], "extra": [ 1, 12, 233, 83, 34, 217, 87, 87, 96, 157, 223, 101, 39, 20, 221, 122, 99, 172, 201, 221, 86, 11, 10, 1, 46, 228, 101, 234, 46, 78, 194, 172, 120, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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