Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2835bfa1ffe4f88b611bbc2e4ca3af81cdc45908807524099238b29c9b33d3e1

Tx prefix hash: ede1b672440bdbc57634fd299fede1b06af5c5c93075371379ecc02bacce9c31
Tx public key: b0fd0c51c683e95529394613e277ef7584cebc623276d92dc66e7161d94d1ac6
Timestamp: 1646227751 Timestamp [UCT]: 2022-03-02 13:29:11 Age [y:d:h:m:s]: 03:055:00:16:40
Block: 449792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 819396 RingCT/type: yes/0
Extra: 01b0fd0c51c683e95529394613e277ef7584cebc623276d92dc66e7161d94d1ac60211000000202e6b1fd5000000000000000000

1 output(s) for total of 19.845071389000 dcy

stealth address amount amount idx
00: 980c23e00b5354d6380ab0cb882454a45d4040ef2d1fb1691526f14c4d4d0f01 19.845071389000 864487 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": 449802, "vin": [ { "gen": { "height": 449792 } } ], "vout": [ { "amount": 19845071389, "target": { "key": "980c23e00b5354d6380ab0cb882454a45d4040ef2d1fb1691526f14c4d4d0f01" } } ], "extra": [ 1, 176, 253, 12, 81, 198, 131, 233, 85, 41, 57, 70, 19, 226, 119, 239, 117, 132, 206, 188, 98, 50, 118, 217, 45, 198, 110, 113, 97, 217, 77, 26, 198, 2, 17, 0, 0, 0, 32, 46, 107, 31, 213, 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