Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91d052b674a2151d10b9ddeb5c395e8eeaaf5ba32575f220a36c7175c3eb2efc

Tx prefix hash: ccf7aa815cefb4acab427fbb25528d213d33f8c366740dc6899516f7c24cdd51
Tx public key: bee40e80d52965ac61e91977cb9eff3f44bdfdc5bcc2d8f50c85106a06d2012f
Timestamp: 1675302696 Timestamp [UCT]: 2023-02-02 01:51:36 Age [y:d:h:m:s]: 01:348:03:16:30
Block: 687869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509789 RingCT/type: yes/0
Extra: 01bee40e80d52965ac61e91977cb9eff3f44bdfdc5bcc2d8f50c85106a06d2012f021100000002e7ace25d000000000000000000

1 output(s) for total of 3.227040278000 dcy

stealth address amount amount idx
00: c47181cee5eba79384800a41a915472cedca975b00b47b3a46ddda75a390d83d 3.227040278000 1130458 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": 687879, "vin": [ { "gen": { "height": 687869 } } ], "vout": [ { "amount": 3227040278, "target": { "key": "c47181cee5eba79384800a41a915472cedca975b00b47b3a46ddda75a390d83d" } } ], "extra": [ 1, 190, 228, 14, 128, 213, 41, 101, 172, 97, 233, 25, 119, 203, 158, 255, 63, 68, 189, 253, 197, 188, 194, 216, 245, 12, 133, 16, 106, 6, 210, 1, 47, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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