Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc0711204d4708cd3cd1deb25d3bc9e9c62704e8e516cfe01412092664115033

Tx prefix hash: cc86c12f51fc658ced598ae3b3eb0d01a5b6265a0b4b6e6795605178f9b64ed5
Tx public key: f5a2326faa1e73ce605db24e0b305cdc0552aa7817354b65d33e0ddc3c258bff
Timestamp: 1583082029 Timestamp [UCT]: 2020-03-01 17:00:29 Age [y:d:h:m:s]: 04:261:01:33:23
Block: 74683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1080448 RingCT/type: yes/0
Extra: 01f5a2326faa1e73ce605db24e0b305cdc0552aa7817354b65d33e0ddc3c258bff0211000001920aca7173000000000000000000

1 output(s) for total of 347.172259807000 dcy

stealth address amount amount idx
00: 9b399aa5eaea470e4ab35d1853bac108e56226b435f06c53506af61c3762723f 347.172259807000 138148 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": 74693, "vin": [ { "gen": { "height": 74683 } } ], "vout": [ { "amount": 347172259807, "target": { "key": "9b399aa5eaea470e4ab35d1853bac108e56226b435f06c53506af61c3762723f" } } ], "extra": [ 1, 245, 162, 50, 111, 170, 30, 115, 206, 96, 93, 178, 78, 11, 48, 92, 220, 5, 82, 170, 120, 23, 53, 75, 101, 211, 62, 13, 220, 60, 37, 139, 255, 2, 17, 0, 0, 1, 146, 10, 202, 113, 115, 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