Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e733c29588c773aa3f607142bd6344bfe5ad8d2cdfa91f167a1152e4aeea0e4d

Tx prefix hash: 95d48c558575f5737132821cfd4b9f7de320c844ef1ef01f53f8548d313f99ce
Tx public key: 06fd614f7fa80ea7bf4163865661021be904f3c20f07a9e94a11dccd698b4347
Timestamp: 1627819158 Timestamp [UCT]: 2021-08-01 11:59:18 Age [y:d:h:m:s]: 03:154:01:05:38
Block: 305174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 882718 RingCT/type: yes/0
Extra: 0106fd614f7fa80ea7bf4163865661021be904f3c20f07a9e94a11dccd698b4347021100000002e6f80b5a000000000000000000

1 output(s) for total of 59.818061809000 dcy

stealth address amount amount idx
00: 61b45f2c591d2afac78e515a00fdda102e931431ab56595986605717980b3ade 59.818061809000 636611 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": 305184, "vin": [ { "gen": { "height": 305174 } } ], "vout": [ { "amount": 59818061809, "target": { "key": "61b45f2c591d2afac78e515a00fdda102e931431ab56595986605717980b3ade" } } ], "extra": [ 1, 6, 253, 97, 79, 127, 168, 14, 167, 191, 65, 99, 134, 86, 97, 2, 27, 233, 4, 243, 194, 15, 7, 169, 233, 74, 17, 220, 205, 105, 139, 67, 71, 2, 17, 0, 0, 0, 2, 230, 248, 11, 90, 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