Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fbe188ba5f072e7e06c7ac19f7b9055435596a8b538cfcf623cbdaaf75d881c

Tx prefix hash: 14e6354e4e563ef2562cfd203f9d807b9ecf2fc9bd8327a41cdd37323e106403
Tx public key: af4acd18fe7ebde2540a28f9a5927f7a03e7aa5dc41de2aff4848a49c21fe53d
Timestamp: 1716077238 Timestamp [UCT]: 2024-05-19 00:07:18 Age [y:d:h:m:s]: 00:300:00:45:04
Block: 1025032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214459 RingCT/type: yes/0
Extra: 01af4acd18fe7ebde2540a28f9a5927f7a03e7aa5dc41de2aff4848a49c21fe53d0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48f2dff4bc85c584d039640a6e38ed323ef0c1750a1b937fc9969494a609be36 0.600000000000 1491239 of 15

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": 1025042, "vin": [ { "gen": { "height": 1025032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48f2dff4bc85c584d039640a6e38ed323ef0c1750a1b937fc9969494a609be36" } } ], "extra": [ 1, 175, 74, 205, 24, 254, 126, 189, 226, 84, 10, 40, 249, 165, 146, 127, 122, 3, 231, 170, 93, 196, 29, 226, 175, 244, 132, 138, 73, 194, 31, 229, 61, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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