Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 287dea177b862827d8dbcf31cb9d48ff2b150a82f3db56453ecab72875d3ebfa

Tx prefix hash: a6591fd0defafb2b6161f6ea7aa606088542fd33f7d25ed2783d1fd966cf4d5c
Tx public key: b46fd61c0d428a26582ba9a36450f3e961f70f56f616775d0af758a61e2db1d5
Timestamp: 1625647306 Timestamp [UCT]: 2021-07-07 08:41:46 Age [y:d:h:m:s]: 03:334:17:09:43
Block: 289600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1009274 RingCT/type: yes/0
Extra: 01b46fd61c0d428a26582ba9a36450f3e961f70f56f616775d0af758a61e2db1d5021100000003d142c209000000000000000000

1 output(s) for total of 67.365181938000 dcy

stealth address amount amount idx
00: 03c455cd098d0a2c7bc74e82b756d22fccb7f37bf920e72479cee8e219a9c587 67.365181938000 606568 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": 289610, "vin": [ { "gen": { "height": 289600 } } ], "vout": [ { "amount": 67365181938, "target": { "key": "03c455cd098d0a2c7bc74e82b756d22fccb7f37bf920e72479cee8e219a9c587" } } ], "extra": [ 1, 180, 111, 214, 28, 13, 66, 138, 38, 88, 43, 169, 163, 100, 80, 243, 233, 97, 247, 15, 86, 246, 22, 119, 93, 10, 247, 88, 166, 30, 45, 177, 213, 2, 17, 0, 0, 0, 3, 209, 66, 194, 9, 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