Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4effd50a4d473934d3c714115da1c1c3047ef644d5ac9fd376c89cb78effc41d

Tx prefix hash: 882643c78f8a2f03438edf1f31fd14983dfb78a7f3441f224655fe424c576bdd
Tx public key: eb19544008e22269e537a07ab79f7bfdc48ed683b2d20dd34de8f93ffbaf634f
Timestamp: 1701953533 Timestamp [UCT]: 2023-12-07 12:52:13 Age [y:d:h:m:s]: 01:192:01:39:25
Block: 907937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398364 RingCT/type: yes/0
Extra: 01eb19544008e22269e537a07ab79f7bfdc48ed683b2d20dd34de8f93ffbaf634f02110000000139e1d5d3000000000000000000

1 output(s) for total of 0.602043384000 dcy

stealth address amount amount idx
00: e3d5e96f1dad1357c8432113b625e168da820c8fb34ef619b4d5910d64ed3b11 0.602043384000 1364934 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": 907947, "vin": [ { "gen": { "height": 907937 } } ], "vout": [ { "amount": 602043384, "target": { "key": "e3d5e96f1dad1357c8432113b625e168da820c8fb34ef619b4d5910d64ed3b11" } } ], "extra": [ 1, 235, 25, 84, 64, 8, 226, 34, 105, 229, 55, 160, 122, 183, 159, 123, 253, 196, 142, 214, 131, 178, 210, 13, 211, 77, 232, 249, 63, 251, 175, 99, 79, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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