Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2c09b19ff1be129b76983b202146a8fd41db57b484156da9795fe1492c32078

Tx prefix hash: 986ac2f445fb39922223905efc7be27c9e6e702864b3133269aa509a0f5ea328
Tx public key: dc7c54e5688d7676540b588c52f59f97c49df7f7d6cd9af50d9c0de4041b0669
Timestamp: 1727931977 Timestamp [UCT]: 2024-10-03 05:06:17 Age [y:d:h:m:s]: 00:194:19:35:29
Block: 1123317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139037 RingCT/type: yes/0
Extra: 01dc7c54e5688d7676540b588c52f59f97c49df7f7d6cd9af50d9c0de4041b066902110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e315a80a385a05f9c6e19d29985817073c5509fdfe788da03671517ace2bf7d6 0.600000000000 1605850 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": 1123327, "vin": [ { "gen": { "height": 1123317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e315a80a385a05f9c6e19d29985817073c5509fdfe788da03671517ace2bf7d6" } } ], "extra": [ 1, 220, 124, 84, 229, 104, 141, 118, 118, 84, 11, 88, 140, 82, 245, 159, 151, 196, 157, 247, 247, 214, 205, 154, 245, 13, 156, 13, 228, 4, 27, 6, 105, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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