Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 443ea2b1c8708b4de7a67cf387203fc958dd0e18524cd561e414a58ca7e0868b

Tx prefix hash: 459434859d3623179eccd5aa94ebf3622106e389df495461431191e49b2f3c2b
Tx public key: dcf21a20eb7e0470b2b3ae6398598d92886b5dd0118638ef57bc1ff6c0f7c2ef
Timestamp: 1630398919 Timestamp [UCT]: 2021-08-31 08:35:19 Age [y:d:h:m:s]: 03:194:18:00:13
Block: 324407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 913703 RingCT/type: yes/0
Extra: 01dcf21a20eb7e0470b2b3ae6398598d92886b5dd0118638ef57bc1ff6c0f7c2ef02110000002e7062e8e6000000000000000000

1 output(s) for total of 51.655061007000 dcy

stealth address amount amount idx
00: 59f9433bf229aede53d26daf5f2a882cc9c30c83cca11179b8eb0ee96e41924b 51.655061007000 672606 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": 324417, "vin": [ { "gen": { "height": 324407 } } ], "vout": [ { "amount": 51655061007, "target": { "key": "59f9433bf229aede53d26daf5f2a882cc9c30c83cca11179b8eb0ee96e41924b" } } ], "extra": [ 1, 220, 242, 26, 32, 235, 126, 4, 112, 178, 179, 174, 99, 152, 89, 141, 146, 136, 107, 93, 208, 17, 134, 56, 239, 87, 188, 31, 246, 192, 247, 194, 239, 2, 17, 0, 0, 0, 46, 112, 98, 232, 230, 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