Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39d41ca0b809620a6abbf60afb6635f8e2a666722b95def5a53e88b2ce6ffb98

Tx prefix hash: eda10e6f3bed3e97c07191b612f8283a95591071295894b053ab012e25a27313
Tx public key: 3729da7bcde51b4c271b053f9a3825862ef958d2d798ca73752d89c6b21fcd2f
Timestamp: 1634579670 Timestamp [UCT]: 2021-10-18 17:54:30 Age [y:d:h:m:s]: 03:067:01:47:57
Block: 355675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 826027 RingCT/type: yes/0
Extra: 013729da7bcde51b4c271b053f9a3825862ef958d2d798ca73752d89c6b21fcd2f021100000014fdc024ec000000000000000000

1 output(s) for total of 40.692673226000 dcy

stealth address amount amount idx
00: 7ae68e5ff8bcf90e90f468ef06d6c73b0daa475465f8a5da633ef1e99e4293db 40.692673226000 726037 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": 355685, "vin": [ { "gen": { "height": 355675 } } ], "vout": [ { "amount": 40692673226, "target": { "key": "7ae68e5ff8bcf90e90f468ef06d6c73b0daa475465f8a5da633ef1e99e4293db" } } ], "extra": [ 1, 55, 41, 218, 123, 205, 229, 27, 76, 39, 27, 5, 63, 154, 56, 37, 134, 46, 249, 88, 210, 215, 152, 202, 115, 117, 45, 137, 198, 178, 31, 205, 47, 2, 17, 0, 0, 0, 20, 253, 192, 36, 236, 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