Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f80af5441281605da5d79f152c37b65a35bb33408ebf07cee07b96caf487603

Tx prefix hash: 06a793276476f3a2dcb0fb1f64b52714eda7df404161c2dab5822a046ee1e670
Tx public key: 3e0c5348a171ffdad87aa3bbe34ebd13afec9caf10e7fb743fbf63d044d15ab4
Timestamp: 1636577414 Timestamp [UCT]: 2021-11-10 20:50:14 Age [y:d:h:m:s]: 03:051:02:47:14
Block: 371638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 815126 RingCT/type: yes/0
Extra: 013e0c5348a171ffdad87aa3bbe34ebd13afec9caf10e7fb743fbf63d044d15ab402110000001a745f00f8000000000000000000

1 output(s) for total of 36.025450767000 dcy

stealth address amount amount idx
00: b7679f5c056e5f1ba488b944a01ed2ae2bf410f8e89985dfd8bfb7fc0740618d 36.025450767000 753062 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": 371648, "vin": [ { "gen": { "height": 371638 } } ], "vout": [ { "amount": 36025450767, "target": { "key": "b7679f5c056e5f1ba488b944a01ed2ae2bf410f8e89985dfd8bfb7fc0740618d" } } ], "extra": [ 1, 62, 12, 83, 72, 161, 113, 255, 218, 216, 122, 163, 187, 227, 78, 189, 19, 175, 236, 156, 175, 16, 231, 251, 116, 63, 191, 99, 208, 68, 209, 90, 180, 2, 17, 0, 0, 0, 26, 116, 95, 0, 248, 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