Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56a3078a2a4816857329a90ad24afd5c70fa26f9fca5d85c828fa0ddbe18de80

Tx prefix hash: febcd6f4ef5bcf30661a98ecd11dc6d7fd3717bacc87f60970a62388e971e873
Tx public key: 8e95724c69a3f5336c7974b4b3727411fa85805ad1229d4b526fe990a1a844c0
Timestamp: 1673457718 Timestamp [UCT]: 2023-01-11 17:21:58 Age [y:d:h:m:s]: 02:087:19:59:58
Block: 672559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 584441 RingCT/type: yes/0
Extra: 018e95724c69a3f5336c7974b4b3727411fa85805ad1229d4b526fe990a1a844c00211000000038b7b6602000000000000000000

1 output(s) for total of 3.626876721000 dcy

stealth address amount amount idx
00: f71a30071384bdd4e64a6b732f1e35c09f313f0286cf1d5c2ef8896aa1c021fd 3.626876721000 1114116 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": 672569, "vin": [ { "gen": { "height": 672559 } } ], "vout": [ { "amount": 3626876721, "target": { "key": "f71a30071384bdd4e64a6b732f1e35c09f313f0286cf1d5c2ef8896aa1c021fd" } } ], "extra": [ 1, 142, 149, 114, 76, 105, 163, 245, 51, 108, 121, 116, 180, 179, 114, 116, 17, 250, 133, 128, 90, 209, 34, 157, 75, 82, 111, 233, 144, 161, 168, 68, 192, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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