Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2f92f07e3c2e4f8bcb8d935c50338d236b484442078347aa35dd3cedbb4a9cb

Tx prefix hash: 14ad249f52315b898dba55262740f49f2a50d74b2585ec16c18e5e4be8b6f01c
Tx public key: c384f52a397c25556786e79a71247f9b67816b0bc256843e4e225bef933ac91d
Timestamp: 1673466982 Timestamp [UCT]: 2023-01-11 19:56:22 Age [y:d:h:m:s]: 02:002:02:13:59
Block: 672637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523388 RingCT/type: yes/0
Extra: 01c384f52a397c25556786e79a71247f9b67816b0bc256843e4e225bef933ac91d02110000000352542ceb000000000000000000

1 output(s) for total of 3.624719027000 dcy

stealth address amount amount idx
00: dfb9a505f0ffa4e034b6ed24e5eed7d1a8b71cfc188b68ac66d33dddf46d506c 3.624719027000 1114198 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": 672647, "vin": [ { "gen": { "height": 672637 } } ], "vout": [ { "amount": 3624719027, "target": { "key": "dfb9a505f0ffa4e034b6ed24e5eed7d1a8b71cfc188b68ac66d33dddf46d506c" } } ], "extra": [ 1, 195, 132, 245, 42, 57, 124, 37, 85, 103, 134, 231, 154, 113, 36, 127, 155, 103, 129, 107, 11, 194, 86, 132, 62, 78, 34, 91, 239, 147, 58, 201, 29, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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